TIBCO Translator Errors
As mentioned in our TIBCO Translator Transition listserv dated 10/12/2016, Palmetto GBA discovered the following differences in editing results between Sybase and TIBCO during Institutional Encounter testing. Please be advised when the TIBCO translator is implemented into production the edits below will apply.
Any extra separator (*) or any invalid character (‘) in the 837 data stream will result in a TIBCO 999 error rejection. For example:
| 999 Error Code | 837 Data Error Explanation | Data Error Explanation |
|---|---|---|
| IK3*HI*121143*2300*8~ CTX*CLM01:EN123456789012~ IK4*5*1270*2*BBQ~ |
HI*BBQ:5A1223Z:D8:20160419*BBQ:5A12 21Z:D8:20160419*BBQ:06BP4ZZ:D8:2016 0419**BBQ:02RF08Z:D8:20160419~ |
Due to the extra separator (*) the BBQ:02RF08Z:D8:20160419 composite begins in the HI05 field and should begin in the HI04 field |
| IK3*N3*45926*2330*8~ CTX*CLM01:1234567890~ IK4*1*166*6*17 TECH CIR` ~ |
N3*17 TECH CIR` ~ N4*COLUMBIA*SC*29203~ |
The N301 was populated with an invalid character (‘). |
All encounters submitted with a Claim Frequency Type Code of ‘7’ must include a REF Segment with an F8 qualifier and the original claim control number being referenced.
| 999 Error Code | 837 Data Error Explanation | Data Error Explanation |
|---|---|---|
| IK3*REF*36688*2300*I6~ CTX*CLM01:123456789~ IK5*R*5~ |
CLM*123456789*411821.51***11|A|7**C*Y*Y~ DTP*096*TM*1700~ DTP*434*RD8*20151027-20151109~ DTP*435*D8*20151027~ CL1*1*1*03~ AMT*F3*0~ REF*D9*111615225686649~ Missing REF*F8 HI*ABK|M4802~ |
The 2300/REF01=F8 was not populated. |
Last Updated: 10/21/2016 10:39:00 AM